CVE-2026-11999
X.509 trust-chain bypass via path-depth exhaustion in wolfSSL_X509_verify_cert()
Description
X.509 trust-chain bypass (path-depth exhaustion) in the OpenSSL compatibility certificate verifier (wolfSSL_X509_verify_cert()). This affects only builds with --enable-opensslextra whose application calls X509_verify_cert() with caller-supplied untrusted intermediates; for those users it is critical, otherwise the library is unaffected. Native wolfSSL TLS/DTLS usage is not impacted. X509_verify_cert() returned success based only on the last verified link rather than on reaching a trust anchor: when the supplied chain is deeper than the verifier's maximum path depth (default 100), path building runs out of depth while still walking untrusted intermediates and the chain is accepted even though it never reaches a configured trust anchor, allowing acceptance of an attacker-controlled certificate. The default TLS handshake (WOLFSSL_VERIFY_PEER) is not affected; only applications doing manual or deferred verification through this API are.
INFO
Published Date :
June 25, 2026, 4:56 p.m.
Last Modified :
June 25, 2026, 4:56 p.m.
Remotely Exploit :
Yes !
Source :
wolfSSL
Affected Products
The following products are affected by CVE-2026-11999
vulnerability.
Even if cvefeed.io is aware of the exact versions of the
products
that
are
affected, the information is not represented in the table below.
No affected product recoded yet
CVSS Scores
| Score | Version | Severity | Vector | Exploitability Score | Impact Score | Source |
|---|---|---|---|---|---|---|
| CVSS 4.0 | HIGH | 50d2cd11-d01a-48ed-9441-5bfce9d63b27 | ||||
| CVSS 4.0 | HIGH | [email protected] |
Solution
- Update wolfSSL to a version with the fix.
- Ensure proper certificate chain validation is used.
- Do not call X509_verify_cert() with untrusted intermediates.
- Avoid --enable-opensslextra if not required.
We scan GitHub repositories to detect new proof-of-concept exploits. Following list is a collection of public exploits and proof-of-concepts, which have been published on GitHub (sorted by the most recently updated).
Results are limited to the first 15 repositories due to potential performance issues.
The following list is the news that have been mention
CVE-2026-11999 vulnerability anywhere in the article.